Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
Historical advisory saved 23 Oct 2026 16:01:25 UTC. The publisher may have updated it since then. Latest advisory.
osv · GHSA-8xfc-gm6g-vgpv
PublishedAn 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.
- Source published
- 14 May 2024 15:32:54 UTC
- Source modified
- 10 Sep 2026 03:49:19 UTC
- Saved here
- 23 Oct 2026 16:01:25 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Publisher rating · MODERATE