Bouncy Castle Java Cryptography API vulnerable to DNS poisoning
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-34447US | — | — | ||
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. W… | ||||
02
references
External citations — patches, advisories, analysis.
- http://security.netapp.com/advisory/ntap-20240614-0007WEB
- https://github.com/bcgit/bc-javaPACKAGE
- https://github.com/bcgit/bc-java/issues/1656WEB
- https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902024%E2%80%9034447WEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-34447ADVISORY
- https://www.bouncycastle.org/latest_releases.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan