dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-8885

MEDIUM · 6.3 CVSS v4.0 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BC-FJA bc-fips on All allows Excessive Allocation. This vulnerability is associated with program files https://github.com/bcgit/bc-java/blob/main/core/src/main/java/org/bouncycastle/asn1/ASN1ObjectIdenti... https://github.com/bcgit/bc-java/blob/main/core/src/main/java/org/bouncycastle/asn1/ASN1ObjectIdentifier.Java . This issue affects BC Java: from 1.0 through 1.77; BC-FJA: from 1.0.0 through 1.0.2.5, from 2.0.0 through 2.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in the ASN1ObjectIdentifier parsing code within Bouncy Castle's BC Java and BC-FJA cryptographic libraries. Without proper resource limits, parsing specially crafted ASN.1 object identifiers can lead to excessive memory allocation, potentially causing denial of service through resource exhaustion.

MitigationUpgrade Bouncy Castle libraries to versions beyond 1.77 (BC Java) and beyond 2.0.1 (BC-FJA). Additionally, implement input validation and resource limits on ASN.1 parsing operations as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:X/R:U/V:X/RE:M/U:Amber

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Bouncy Castle library usage
    Search your project dependencies (Maven pom.xml, Gradle build.gradle, or JAR files in lib/ directory) for bcprov, bcpkix, or bc-fips libraries
    Affected if Any Bouncy Castle library is present in the runtime environment
  2. Determine BC Java version
    Locate the bcprov-*.jar file or dependency declaration and note the version number (e.g., bcprov-jdk18on-1.76.jar)
    Affected if Version is below 1.77
  3. Determine BC-FJA version
    Locate the bc-fips-*.jar or bcpkix-*.jar file or dependency and note the version number
    Affected if Version is below 2.0.1
  4. Verify ASN.1 Object Identifier parsing is used
    Search codebase for imports of org.bouncycastle.asn1.* and usage of ASN1ObjectIdentifier, ASN1InputStream, or ASN1Primitive.getInstance() methods
    Affected if Application code parses ASN.1 object identifiers from untrusted input
  5. Check if resource limits are enforced on ASN.1 parsing
    Review code that performs ASN.1 parsing and verify if resource constraints (e.g., size limits, timeout, streaming with limits) are configured on the parsing context or input stream
    Affected if No resource limits are implemented on ASN.1 parsing operations

You are affected if you run BC Java below 1.77 or BC-FJA below 2.0.1, parse ASN.1 object identifiers from external input, and lack resource limits on ASN.1 parsing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Bouncy Castle libraries to versions beyond 1.77 (BC Java) and beyond 2.0.1 (BC-FJA). Additionally, implement input validation and resource limits on ASN.1 parsing operations as a defense-in-depth measure.

Recommended fix Moderate confidence

BC Java: 1.78 or later; BC-FJA: 1.0.2.6+ (1.x) or 2.0.2+ (2.x)

  1. 1. Identify all Java projects that depend on BC Java (bcprov) or BC-FJA (bc-fips) libraries
  2. 2. For each project, check the current dependency version using build tools (Maven: mvn dependency:tree, Gradle: gradle dependencies)
  3. 3. Update BC Java dependency to version 1.78 or later
  4. 4. Update BC-FJA dependency to version 1.0.2.6 or later for the 1.x line, or version 2.0.2 or later for the 2.x line
  5. 5. Rebuild and test applications to verify functionality is maintained
  6. 6. Deploy updated applications to production environments
Caveat Review release notes between affected and fixed versions for any API changes or deprecations that may affect your application

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8885 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data