NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven.NET NuGet
Not in CISA KEV
MEDIUM severity

Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")GHSA-v435-xc8x-wvr9

MEDIUMFix: bcgit/bc-csharp@c984b8b

GHSA-v435-xc8x-wvr9 is a medium-severity (CVSS 5.9) CWE-203 vulnerability in org.bouncycastle:bctls-fips. A fix is available for org.bouncycastle:bctls-fips — see the affected versions and patch details below.

Also known asCVE-2024-30171
Published
Updated
Affected
10 pkgs
Patched
9 / 10
Exploits
None indexed
Exploitation data as of Nov 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 GHSA-v435-xc8x-wvr9.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.93%1.40%0.1%0.9%0.9%0.9%0.9%Jun 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

10 pkgs affected
☕org.bouncycastle:bctls-fips☕org.bouncycastle:bcprov-jdk18on☕org.bouncycastle:bcprov-jdk15on☕org.bouncycastle:bcprov-jdk15to18☕org.bouncycastle:bcprov-jdk14☕org.bouncycastle:bctls-jdk18on☕org.bouncycastle:bctls-jdk14☕org.bouncycastle:bctls-jdk15to18+2 more

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 Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.

Affected Packages

10 total 9 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.bouncycastle:bctls-fipsall versions1.0.19org.bouncycastle:bctls-fips:1.0.19
☕Mavenorg.bouncycastle:bcprov-jdk18onall versions1.78org.bouncycastle:bcprov-jdk18on:1.78
☕Mavenorg.bouncycastle:bcprov-jdk15onall versions1.78org.bouncycastle:bcprov-jdk15on:1.78
☕Mavenorg.bouncycastle:bcprov-jdk15to18all versions1.78org.bouncycastle:bcprov-jdk15to18:1.78
☕Mavenorg.bouncycastle:bcprov-jdk14all versions1.78org.bouncycastle:bcprov-jdk14:1.78
☕Mavenorg.bouncycastle:bctls-jdk18onall versions1.78org.bouncycastle:bctls-jdk18on:1.78

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:bctls-fips, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.bouncycastle:bctls-fips to 1.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v435-xc8x-wvr9 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
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 GHSA-v435-xc8x-wvr9 (CC BY 4.0)
ProductFixed inAdvisory
Cryostat 3 on RHEL 8cryostat-tech-preview/cryostat-db-rhel8:3.0.0-3RHSA-2024:4173
Red Hat AMQ Broker 7org.bouncycastle-bcprov-jdk18onRHSA-2024:4271
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2org.bouncycastle-bcprov-jdk18onRHSA-2024:4884
Red Hat Build of Apache Camel 4.4 for Quarkus 3.8see advisoryRHSA-2024:4505
Red Hat build of Quarkus 3.8.5.redhatorg.bouncycastle/bcprov-jdk18on:1.78.1.redhat-00002RHSA-2024:4326
Red Hat JBoss Enterprise Application Platformorg.bouncycastle/bcprov-jdk18on:1.78.1.redhat-00002RHSA-2024:5147
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el8eapRHSA-2024:5144
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el9eapRHSA-2024:5145

Frequently Asked Questions

An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.
O3 Security · Impact-Aware SCA

Is GHSA-v435-xc8x-wvr9 in your dependencies?

Find it across Maven, NuGet, including transitive dependencies.

Bouncy Castle affected by timing side-channel for RSA…