CVE-2025-42976
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 · uneditedSAP NetWeaver Application Server ABAP (BIC Document) allows an authenticated attacker to craft a request that, when submitted to a BIC Document application, could cause a memory corruption error. On successful exploitation, this results in the crash of the target component. Multiple submissions can make the target completely unavailable. A similarly crafted submission can be used to perform an out-of-bounds read operation as well, revealing sensitive information that is loaded in memory at that time. There is no ability to modify any information.
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 · high confidenceA memory corruption vulnerability exists in SAP NetWeaver Application Server ABAP's BIC Document application. An authenticated attacker can craft malicious requests that cause memory corruption, leading to component crashes and denial of service. The same technique can be leveraged for out-of-bounds read operations, exposing sensitive data from memory without the ability to modify information.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP NetWeaver ABAP installationExecute transaction SM51 to display the SAP NetWeaver Application Server ABAP instances running in your environment. Confirm the release and kernel versions displayed.Affected if The system is running SAP NetWeaver Application Server ABAP with the BIC Document application component.
-
Confirm BIC Document component is activeUse transaction SICF to check if the BIC Document service (/sap/bc/rest/... or related BIC document handlers) is active in the SAP system. Check the ICF path tree under the relevant BIC document service nodes.Affected if The BIC Document ICF service is active and accessible in the SAP system.
-
Check installed SAP NetWeaver versionExecute transaction SLICENSE or use SAPMMC to view the installed SAP NetWeaver AS ABAP version and patch level. Compare against any SAP security notes related to CVE-2025-42976.Affected if The installed SAP NetWeaver ABAP version and patch level have not been updated to include the CVE-2025-42976 fix.
-
Review system logs for BIC Document crashesExamine transaction SM37, ST22, and system logs (transaction SM21) for recent ABAP dumps or component crashes related to the BIC Document application or associated memory corruption patterns.Affected if Recent ABAP dumps or crashes in the logs reference BIC Document functionality or memory access violations.
-
Inspect HTTP access logs for suspicious BIC Document requestsCheck transaction SLG1 or the ICM access logs for incoming requests to BIC Document endpoints that exhibit abnormal patterns, large payload sizes, or repeated requests from authenticated users.Affected if Logs show suspicious or malformed requests to BIC Document endpoints that could indicate exploitation attempts.
A system is affected if it runs SAP NetWeaver AS ABAP with the BIC Document component active and the installed version lacks the CVE-2025-42976 security patch.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the relevant SAP security patch for CVE-2025-42976 through the SAP Maintenance Planner or Software Update Manager (SUM). Validate that BIC Document functionality operates normally after patching and implement monitoring for repeated crash patterns as a potential exploitation indicator.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42976 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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