Skip to content

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

Moderate severity GitHub Reviewed Published May 14, 2024 to the GitHub Advisory Database • Updated Dec 6, 2024

Package

nuget BouncyCastle (NuGet)

Affected versions

< 2.3.1

Patched versions

None
nuget BouncyCastle.Cryptography (NuGet)
< 2.3.1
2.3.1
maven org.bouncycastle:bc-fips (Maven)
< 1.0.2.5
1.0.2.5
maven org.bouncycastle:bcprov-jdk14 (Maven)
< 1.78
1.78
maven org.bouncycastle:bcprov-jdk15on (Maven)
< 1.78
1.78
maven org.bouncycastle:bcprov-jdk15to18 (Maven)
< 1.78
1.78
maven org.bouncycastle:bcprov-jdk18on (Maven)
< 1.78
1.78
maven org.bouncycastle:bctls-jdk14 (Maven)
< 1.78
1.78
maven org.bouncycastle:bctls-jdk15to18 (Maven)
< 1.78
1.78
maven org.bouncycastle:bctls-jdk18on (Maven)
< 1.78
1.78

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.

References

Published by the National Vulnerability Database May 14, 2024
Published to the GitHub Advisory Database May 14, 2024
Reviewed May 14, 2024
Last updated Dec 6, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Weaknesses

CVE ID

CVE-2024-29857

GHSA ID

GHSA-8xfc-gm6g-vgpv

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.