First published: Fri May 03 2024(Updated: )
An issue was discovered in Bouncy Castle Java Cryptography APIs before BC 1.78. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be performed against a DNS-resolved IP address in some situations, opening up a possibility of DNS poisoning.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.bouncycastle:bcprov-jdk12 | >=1.61<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk13 | >=1.61<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk15to18 | >=1.61<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk18on | >=1.61<1.78 | 1.78 |
redhat/BC | <1.78 | 1.78 |
IBM Planning Analytics | <=2.1 | |
IBM Planning Analytics | <=2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-34447 has a high severity due to potential vulnerabilities in SSL socket communication when hostname verification is inadequate.
To fix CVE-2024-34447, upgrade to Bouncy Castle version 1.78 or later.
CVE-2024-34447 affects Bouncy Castle Java Cryptography APIs versions prior to 1.78.
CVE-2024-34447 may allow an attacker to perform man-in-the-middle attacks if hostname verification fails.
CVE-2024-34447 affects various packages under Bouncy Castle, including those used in IBM Planning Analytics.