Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2024-34447 — bcprov-jdk18on

MEDIUM

CVE-2024-34447 is a medium-severity (CVSS 5.9) CWE-297 vulnerability in org.bouncycastle:bcprov-jdk18on. A fix is available for org.bouncycastle:bcprov-jdk18on — see the affected versions and patch details below.

Bouncy Castle Java Cryptography API vulnerable to DNS poisoning

Also known asGHSA-4h8f-2wvx-gg5w
Published
Updated
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-34447.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.42%0.85%1.27%0.1%0.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2024-34447 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 386,684 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

7 pkgs affected
☕org.bouncycastle:bcprov-jdk18on☕org.bouncycastle:bcprov-jdk15to18☕org.bouncycastle:bcprov-jdk14☕org.bouncycastle:bcprov-jdk12☕org.bouncycastle:bctls-fips☕org.bouncycastle:bcprov-lts8on☕org.bouncycastle:bcprov-jdk15on

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.bouncycastle:bcprov-jdk18on≥ 1.61&&< 1.781.78org.bouncycastle:bcprov-jdk18on:1.78
☕Mavenorg.bouncycastle:bcprov-jdk15to18≥ 1.61&&< 1.781.78org.bouncycastle:bcprov-jdk15to18:1.78
☕Mavenorg.bouncycastle:bcprov-jdk14≥ 1.61&&< 1.781.78org.bouncycastle:bcprov-jdk14:1.78
☕Mavenorg.bouncycastle:bcprov-jdk12≥ 1.61&&< 1.781.78org.bouncycastle:bcprov-jdk12:1.78
☕Mavenorg.bouncycastle:bctls-fipsall versions1.0.19org.bouncycastle:bctls-fips:1.0.19
☕Mavenorg.bouncycastle:bcprov-lts8onall versions2.73.6org.bouncycastle:bcprov-lts8on:2.73.6

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk18on, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.bouncycastle:bcprov-jdk18on to 1.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-34447 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The vulnerability in Bouncy Castle Java Cryptography APIs, allowing for incorrect resolution of domain names during SSL/TLS connections without explicitly specifying a hostname, is assessed as moderate severity due to its potential impact on security. By exploiting this flaw, an attacker could manipulate DNS…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-34447 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat AMQ Broker 7org.bouncycastle:bcprov-jdk18onRHSA-2024:4271
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2see advisoryRHSA-2024:4884
Red Hat build of Quarkus 3.8.5.redhatorg.bouncycastle/bcprov-jdk18on:1.78.1.redhat-00002RHSA-2024:4326
UbuntuHIGH
USN-8108-1Ubuntu

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-34447 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-34447: bcprov-jdk18on — Fixed in 1.78