Skip to content

Bouncy Castle Java Cryptography API vulnerable to DNS poisoning

Moderate severity GitHub Reviewed Published May 3, 2024 to the GitHub Advisory Database • Updated Jun 24, 2025

Package

maven org.bouncycastle:bcprov-jdk12 (Maven)

Affected versions

>= 1.61, < 1.78

Patched versions

1.78
maven org.bouncycastle:bcprov-jdk14 (Maven)
>= 1.61, < 1.78
1.78
maven org.bouncycastle:bcprov-jdk15to18 (Maven)
>= 1.61, < 1.78
1.78
maven org.bouncycastle:bcprov-jdk18on (Maven)
>= 1.61, < 1.78
1.78
maven org.bouncycastle:bcprov-lts8on (Maven)
< 2.73.6
2.73.6
maven org.bouncycastle:bctls-fips (Maven)
< 1.0.19
1.0.19

Description

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.

References

Published by the National Vulnerability Database May 3, 2024
Published to the GitHub Advisory Database May 3, 2024
Reviewed May 3, 2024
Last updated Jun 24, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(35th percentile)

Weaknesses

Improper Validation of Certificate with Host Mismatch

The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host. Learn more on MITRE.

CVE ID

CVE-2024-34447

GHSA ID

GHSA-4h8f-2wvx-gg5w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.