@fastify/reply-from is vulnerable to Improper Certificate Validation
74
CVE Score
High
Improper Certificate Validation
Before the fix, getUndiciOptions, getHttpOpts and getHttp2Opts in @fastify/reply-from forced rejectUnauthorized to false on all three built-in HTTPS transports whenever the application did not set it, so proxying to an https:// upstream skipped TLS certificate verification by default, including with partial option objects like tls: {}. An on-path network attacker could impersonate the upstream, read forwarded credentials and request bodies, and return forged responses the application trusts. The fix removes the forced value so Node.js and undici verify the upstream certificate by default; self-signed or private-CA upstreams now need an explicit ca or rejectUnauthorized: false.
Upgrade the @fastify/reply-from package to 12.7.0 or later.
You are affected if you are using a version that falls within the vulnerable range and proxy requests to an https:// upstream without explicitly setting rejectUnauthorized on the undici, http or http2 transport options.
7.0.0 - 12.6.5
Fixed in 12.7.0@fastify/reply-from is vulnerable to Improper Certificate Validation in versions 7.0.0 - 12.6.5.
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.