bctls-lts8on is vulnerable to Improper Certificate Validation
78
High Risk
HostnameUtil gates the JSSE hostname verifier's 'match CN when no dNSName SAN exists' fallback with Properties.isOverrideSet(JSSE_HOSTNAME_CHECK_CN_FALLBACK, true), and the two-argument form returns that default when the property is unset. Documentation says the unset default must disable the fallback, but every deployment that does not explicitly set the property to false therefore keeps CN-fallback active. RFC 5280 name constraints only constrain SAN entries of the constrained type, so a leaf with no dNSName SAN can pass a dNSName-constrained chain while HostnameUtil still accepts an attacker-chosen CN that matches the target hostname, weakening TLS hostname verification. The fix calls the single-argument isOverrideSet so CN-fallback stays disabled unless the property is explicitly enabled.
You are affected if you are using a version that falls within the vulnerable range and your application uses the Bouncy Castle JSSE provider for TLS hostname verification without explicitly setting JSSE_HOSTNAME_CHECK_CN_FALLBACK to false.
bctls-lts8on is vulnerable to Improper Certificate Validation in versions 2.73.0 - 2.73.11.
Upgrade the org.bouncycastle:bctls-lts8on library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant