All reports
Medium

Bouncy Castle Java Cryptography API vulnerable to DNS poisoning

Affected versions

Affected versions
>= 1.61, < 1.78
Fixed version
1.78
Affected versions
>= 1.61, < 1.78
Fixed version
1.78
Affected versions
>= 1.61, < 1.78
Fixed version
1.78
Affected versions
>= 1.61, < 1.78
Fixed version
1.78
Affected versions
>= 1.61, < 1.78
Fixed version
1.78
Affected versions
< 2.73.6
Fixed version
2.73.6
Affected versions
< 1.0.19
Fixed version
1.0.19
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-34447

Probability of exploitation in the next 30 days: 0.77%

FIRST EPSS · 2026-11-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.

Links

Credits

  • samueloph
  • binary-1024
  • hmolsen
  • kmoens