Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2024-29857: 1.10% estimated exploitation activity in the next 30 days; percentile 65.72 (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 ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC Java) before 1.78, BC Java LTS before 2.73.6, BC-FJA before 1.0.2.5, and BC C

.Net before 2.3.1. Importing an EC certificate with crafted F2m parameters can lead to excessive CPU consumption during the evaluation of the curve parameters.

Published by the source

14 May 2024, 15:32 UTC

Last modified by the source

6 Dec 2024, 15:32 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8xfc-gm6g-vgpv

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

# Patch Next advisory brief: CVE-2024-29857

Advisory: Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
IDs: CVE-2024-29857, GHSA-8xfc-gm6g-vgpv
Record: https://patchnext.com/advisories/cve-2024-29857 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.bouncycastle:bc-fips 1.0.2.5; org.bouncycastle:bcprov-jdk14 1.78; org.bouncycastle:bcprov-jdk15to18 1.78; org.bouncycastle:bctls-jdk15to18 1.78; 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:bc-fips: affected < 1.0.2.5; fixed in 1.0.2.5
- 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-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:bc-fips: check the installed version with your package manager.
- 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-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:bc-fips, org.bouncycastle:bcprov-jdk14, org.bouncycastle:bcprov-jdk15to18, org.bouncycastle:bctls-jdk15to18, 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-8xfc-gm6g-vgpv (GitHub-reviewed advisory GHSA-8xfc-gm6g-vgpv lists affected ranges: Maven org.bouncycastle:bcprov-jdk18on >=0 =0 =0 =0 =0 =0 =0 =0 <1.0.2.5)

Commands are suggestions: review each one before running it.