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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-30171: 0.90% estimated exploitation activity in the next 30 days; percentile 59.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

14 May 2024, 15:32 UTC

Last modified by the source

9 Sep 2024, 21:27 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v435-xc8x-wvr9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-30171

Advisory: Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")
IDs: CVE-2024-30171, GHSA-v435-xc8x-wvr9
Record: https://patchnext.com/advisories/cve-2024-30171 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.bouncycastle:bcprov-jdk14 1.78; org.bouncycastle:bcprov-jdk15to18 1.78; org.bouncycastle:bctls-jdk15to18 1.78; org.bouncycastle:bctls-fips 1.0.19; org.bouncycastle:bctls-jdk14 1.78; org.bouncycastle:bcprov-jdk18on 1.78; org.bouncycastle:bctls-jdk18on 1.78; org.bouncycastle:bcprov-jdk15on 1.78. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.bouncycastle:bcprov-jdk14: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bcprov-jdk15to18: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bctls-jdk15to18: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bctls-fips: affected < 1.0.19; fixed in 1.0.19
- Maven org.bouncycastle:bctls-jdk14: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bcprov-jdk18on: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bctls-jdk18on: affected < 1.78; fixed in 1.78
- Maven org.bouncycastle:bcprov-jdk15on: affected < 1.78; fixed in 1.78

## Suggested inspection (read-only)
- Maven org.bouncycastle:bcprov-jdk14: check the installed version with your package manager.
- Maven org.bouncycastle:bcprov-jdk15to18: check the installed version with your package manager.
- Maven org.bouncycastle:bctls-jdk15to18: check the installed version with your package manager.
- Maven org.bouncycastle:bctls-fips: check the installed version with your package manager.
- Maven org.bouncycastle:bctls-jdk14: check the installed version with your package manager.
- Maven org.bouncycastle:bcprov-jdk18on: check the installed version with your package manager.
- Maven org.bouncycastle:bctls-jdk18on: check the installed version with your package manager.
- Maven org.bouncycastle:bcprov-jdk15on: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.bouncycastle:bcprov-jdk14, org.bouncycastle:bcprov-jdk15to18, org.bouncycastle:bctls-jdk15to18, org.bouncycastle:bctls-fips, org.bouncycastle:bctls-jdk14, org.bouncycastle:bcprov-jdk18on, org.bouncycastle:bctls-jdk18on, org.bouncycastle:bcprov-jdk15on.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v435-xc8x-wvr9 (GitHub-reviewed advisory GHSA-v435-xc8x-wvr9 lists affected ranges: Maven org.bouncycastle:bctls-fips >=0 =0 =0 =0 =0 =0 =0 =0 <1.78)

Commands are suggestions: review each one before running it.