CVE-2026-63578: CWE-770 Allocation of Resources Without Limits or Throttling in Legion of the Bouncy Castle Inc. bc-csharp
Allocation of resources without limits in password-based private-key decryption (PbeUtilities.GenerateCipherParameters) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply an encrypted private key, such as a PKCS#8 EncryptedPrivateKeyInfo or "ENCRYPTED PRIVATE KEY" PEM file, to cause a denial of service through CPU exhaustion via an iteration count close to 2^31, because the count is taken from the unauthenticated algorithm parameters without an upper bound and the key derivation runs before the password or the data can be checked. PKCS#5 PBES1 and PBES2 (PBKDF2), the PKCS#12 PBE algorithms and CMS password recipients (CmsPbeKey) are affected. Loading PKCS#12 files with Pkcs12Store is covered by CVE-2026-63572, and a zero or negative count with the PKCS#12 algorithms by CVE-2026-63575.
AI Analysis
Technical Summary
The vulnerability CVE-2026-63578 in bc-csharp before 2.7.0 arises from unbounded resource allocation during password-based private-key decryption in the PbeUtilities.GenerateCipherParameters method. The iteration count used in key derivation is extracted from unauthenticated algorithm parameters without an upper limit, enabling an attacker who can supply an encrypted private key (e.g., PKCS#8 EncryptedPrivateKeyInfo or PEM files) to cause CPU exhaustion and denial of service by specifying an iteration count close to 2^31. This affects multiple password-based encryption schemes including PKCS#5 PBES1, PBES2 (PBKDF2), PKCS#12 PBE algorithms, and CMS password recipients. The key derivation process occurs before password or data validation, making early exhaustion possible. Related vulnerabilities in PKCS#12 file handling are addressed separately.
Potential Impact
An unauthenticated attacker capable of supplying a crafted encrypted private key can cause a denial of service by exhausting CPU resources. This can disrupt applications using the vulnerable bc-csharp library for password-based private-key decryption. The vulnerability does not involve data compromise or privilege escalation but can degrade service availability.
Mitigation Recommendations
A fixed version 2.7.0 or later of bc-csharp addresses this issue by imposing limits on iteration counts during key derivation. Users should upgrade to version 2.7.0 or newer to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes. Patch status is confirmed by the version boundary in the affectedVersions field.
CVE-2026-63578: CWE-770 Allocation of Resources Without Limits or Throttling in Legion of the Bouncy Castle Inc. bc-csharp
Description
Allocation of resources without limits in password-based private-key decryption (PbeUtilities.GenerateCipherParameters) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply an encrypted private key, such as a PKCS#8 EncryptedPrivateKeyInfo or "ENCRYPTED PRIVATE KEY" PEM file, to cause a denial of service through CPU exhaustion via an iteration count close to 2^31, because the count is taken from the unauthenticated algorithm parameters without an upper bound and the key derivation runs before the password or the data can be checked. PKCS#5 PBES1 and PBES2 (PBKDF2), the PKCS#12 PBE algorithms and CMS password recipients (CmsPbeKey) are affected. Loading PKCS#12 files with Pkcs12Store is covered by CVE-2026-63572, and a zero or negative count with the PKCS#12 algorithms by CVE-2026-63575.
CVSS v4.0
Score 7.1high
Affected software
Legion of the Bouncy Castle Inc.
bc-csharp
pkg:nuget/BouncyCastle.CryptographyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-63578 in bc-csharp before 2.7.0 arises from unbounded resource allocation during password-based private-key decryption in the PbeUtilities.GenerateCipherParameters method. The iteration count used in key derivation is extracted from unauthenticated algorithm parameters without an upper limit, enabling an attacker who can supply an encrypted private key (e.g., PKCS#8 EncryptedPrivateKeyInfo or PEM files) to cause CPU exhaustion and denial of service by specifying an iteration count close to 2^31. This affects multiple password-based encryption schemes including PKCS#5 PBES1, PBES2 (PBKDF2), PKCS#12 PBE algorithms, and CMS password recipients. The key derivation process occurs before password or data validation, making early exhaustion possible. Related vulnerabilities in PKCS#12 file handling are addressed separately.
Potential Impact
An unauthenticated attacker capable of supplying a crafted encrypted private key can cause a denial of service by exhausting CPU resources. This can disrupt applications using the vulnerable bc-csharp library for password-based private-key decryption. The vulnerability does not involve data compromise or privilege escalation but can degrade service availability.
Mitigation Recommendations
A fixed version 2.7.0 or later of bc-csharp addresses this issue by imposing limits on iteration counts during key derivation. Users should upgrade to version 2.7.0 or newer to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes. Patch status is confirmed by the version boundary in the affectedVersions field.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- bcorg
- Date Reserved
- 2026-07-16T23:51:51.307Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abf5de7a43b0b3b8988eab2
Added to database: 10/02/2026, 07:31:51 UTC
Last enriched: 10/02/2026, 07:46:03 UTC
Last updated: 10/02/2026, 21:45:56 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.