All reports
Medium

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

Affected versions

Affected versions
< 1.0.2.5
Fixed version
1.0.2.5
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 1.78
Fixed version
1.78
Affected versions
< 2.3.1
Fixed version
2.3.1
Affected versions
< 2.3.1
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-29857

Probability of exploitation in the next 30 days: 1.10%

FIRST EPSS · 2026-11-18

Description

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.

Links

Credits

  • levpachmanov