CVE-2024-34447GHSA-4H8F-2WVX-GG5W
An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.78, 1.0.19, 2.73.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.6) and before BC FIPS TLS Java 1.0.19. 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- org.bouncycastle:bcprov-jdk18onMaven
From 1.61 · fixed in 1.78
- org.bouncycastle:bcprov-jdk15to18Maven
From 1.61 · fixed in 1.78
- org.bouncycastle:bcprov-jdk14Maven
From 1.61 · fixed in 1.78
- org.bouncycastle:bcprov-jdk12Maven
From 1.61 · fixed in 1.78
- org.bouncycastle:bctls-fipsMaven
fixed in 1.0.19
- org.bouncycastle:bcprov-lts8onMaven
fixed in 2.73.6
- org.bouncycastle:bcprov-jdk15onMaven
From 1.61 · fixed in 1.78