node is vulnerable to Improper Certificate Validation
74
CVE Score
High
Improper Certificate Validation
tls.checkServerIdentity normalizes the hostname with domainToASCII and can match that form to a certificate. Spellings such as 0127.0.0.1, 0x7f.0.0.1, and 2130706433 normalize to one address while the operating system resolver connects to another. The certificate check then succeeds for a different host than the one the socket reaches. The fix rejects hostnames that net.isIP accepts only after normalization.
Upgrade the node and/or the nodejs library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and TLS connects to a non-canonical IP hostname.
22.23.0 - 22.23.3
Fixed in 22.23.424.17.0 - 24.22.0
Fixed in 24.22.126.3.1 - 26.12.0
Fixed in 26.12.1node is vulnerable to Improper Certificate Validation in versions 22.23.0 - 22.23.3, 24.17.0 - 24.22.0 and 26.3.1 - 26.12.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.