undici is vulnerable to Improper Certificate Validation
74
CVE Score
High
Improper Certificate Validation
Agent deep-clones its constructor options with JSON before forwarding them to each per-origin Pool, which silently drops function-valued tls options such as a caller-supplied checkServerIdentity. A certificate the application was written to reject (e.g. for certificate or public-key pinning) is then accepted if it still passes Node's default hostname and chain checks. Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, and EnvHttpProxyAgent is also affected on its direct and NO_PROXY routes. Passing the same options through connect is not affected. The fix preserves the tls option outside the JSON clone so custom verification callbacks reach each origin.
Upgrade the undici library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you pass a function-valued tls option (such as a custom checkServerIdentity) to an Agent or EnvHttpProxyAgent.
4.0.0 - 6.29.0
Fixed in 6.29.17.0.0 - 7.30.0
Fixed in 7.30.18.0.0 - 8.12.1
Fixed in 8.12.2undici is vulnerable to Improper Certificate Validation in versions 4.0.0 - 6.29.0, 7.0.0 - 7.30.0 and 8.0.0 - 8.12.1.
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.