CVE-2024-34447
May 3, 2024, 4:15 p.m.
None
No Score
Description
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.
Product(s) Impacted
| Product | Versions |
|---|---|
| Bouncy Castle Java Cryptography APIs |
|
Weaknesses
Common security weaknesses mapped to this vulnerability.
Tags
Timeline
Published: May 3, 2024, 4:15 p.m.
Last Modified: May 3, 2024, 4:15 p.m.
Last Modified: May 3, 2024, 4:15 p.m.
Status : Received
CVE has been recently published to the CVE List and has been received by the NVD.
More infoSource
cve@mitre.org
*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.