This vulnerability allows attackers to impersonate a trusted host.
Why is this an issue?
Transport Layer Security (TLS) provides secure communication between systems over the internet by encrypting the data sent between them. In this
process, the role of hostname validation, combined with certificate validation, is to ensure that a system is indeed the one it claims to be, adding
an extra layer of trust and security.
When hostname validation is disabled, the client skips this critical check. This creates an opportunity for attackers to pose as a trusted entity
and intercept, manipulate, or steal the data being transmitted.
To do so, an attacker would obtain a valid certificate authenticating example.com, serve it using a different hostname, and the
application code would still accept it.
What is the potential impact?
Establishing trust in a secure way is a non-trivial task. When you disable hostname validation, you are removing a key mechanism designed to build
this trust in internet communication, opening your system up to a number of potential threats.
Identity spoofing
If a system does not validate hostnames, it cannot confirm the identity of the other party involved in the communication. An attacker can exploit
this by creating a fake server and masquerading it as a legitimate one. For example, they might set up a server that looks like your bank’s server,
tricking your system into thinking it is communicating with the bank. This scenario, called identity spoofing, allows the attacker to collect any data
your system sends to them, potentially leading to significant data breaches.
How to fix it in Node.js
Code examples
The following code contains examples of disabled hostname validation.
The hostname validation gets disabled by overriding checkServerIdentity with an empty implementation. It is highly recommended to use
the original implementation.
Noncompliant code example
const https = require('node:https');
let options = {
hostname: 'www.example.com',
port: 443,
path: '/',
method: 'GET',
checkServerIdentity: function() {}, // Noncompliant
secureProtocol: 'TLSv1_2_method'
};
let req = https.request(options, (res) => {
res.on('data', (d) => {
process.stdout.write(d);
});
});
const tls = require('node:tls');
let options = {
checkServerIdentity: function() {}, // Noncompliant
secureProtocol: 'TLSv1_2_method'
};
let socket = tls.connect(443, "www.example.com", options, () => {
process.stdin.pipe(socket);
process.stdin.resume();
});
Compliant solution
const https = require('node:https');
let options = {
hostname: 'www.example.com',
port: 443,
path: '/',
method: 'GET',
secureProtocol: 'TLSv1_2_method'
};
let req = https.request(options, (res) => {
res.on('data', (d) => {
process.stdout.write(d);
});
});
const tls = require('node:tls');
let options = {
secureProtocol: 'TLSv1_2_method'
};
let socket = tls.connect(443, "www.example.com", options, () => {
process.stdin.pipe(socket);
process.stdin.resume();
});
How does this work?
To fix the vulnerability of disabled hostname validation, it is strongly recommended to first re-enable the default validation and fix the root
cause: the validity of the certificate.
Use valid certificates
If a hostname validation failure prevents connecting to the target server, keep in mind that one system’s code should not work around
another system’s problems, as this creates unnecessary dependencies and can lead to reliability issues.
Therefore, the first solution is to change the remote host’s certificate to match its identity. If the remote host is not under your control,
consider replicating its service to a server whose certificate you can change yourself.
In case the contacted host is located on a development machine, and if there is no other choice, try following this solution:
- Create a self-signed certificate for that machine.
- Add this self-signed certificate to the system’s trust store.
- If the hostname is not
localhost, add the hostname in the /etc/hosts file.
Resources
Standards
