CVE-2025-42877
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 Web Dispatcher, Internet Communication Manager (ICM), and SAP Content Server allow an unauthenticated user to exploit logical errors that lead to a memory corruption vulnerability. This results in high impact on the availability with no impact on confidentiality or integrity of the application.
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 confidenceSAP Web Dispatcher, Internet Communication Manager (ICM), and SAP Content Server contain logical errors that can be exploited by unauthenticated remote attackers, leading to memory corruption. This results in significant availability impact while maintaining confidentiality and integrity.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check for SAP Web Dispatcher installation and versionLocate the sapwebdisp executable or check SAP system information using SAP MII version tools, or query SAP kernel version via SM51 transaction or SAP support bundleAffected if Web Dispatcher version falls within the affected version range and the component is actively running as a reverse proxy/load balancer
-
Check for SAP Internet Communication Manager (ICM) statusVerify ICM process is running via SAP transaction SMICM or by checking icman process on the server, or review ICM ports (like 8000, 80, 443) in useAffected if ICM is enabled and running with an affected version of the SAP kernel
-
Check for SAP Content Server installation and versionIdentify Content Server instances via SAP transaction RZ04 or by locating the Content Server software components in the SAP system landscapeAffected if Content Server component is installed and running with an affected version number
-
Verify Web Dispatcher is configured as public-facingReview SAP Web Dispatcher profile parameters (icm/server_port_*) and check if public internet exposure is configured in the web dispatcher administration (WDADMIN)Affected if Web Dispatcher is exposed to unauthenticated remote network traffic on open ports
-
Confirm ICM HTTP/HTTPS ports are externally accessibleCheck SAP profile parameters for icm/listen and network exposure, verify firewall rules allow external access to SAP ICM portsAffected if ICM ports are reachable from untrusted networks without authentication barriers
The environment is affected if any of the three components (Web Dispatcher, ICM, or Content Server) are running and their installed versions match the affected ranges in SAP security notes for this CVE, with network exposure enabling unauthenticated remote access.
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 SAP security patches for affected components (Web Dispatcher, ICM, Content Server) per SAP security notes to remediate the logical errors causing memory corruption.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42877 — 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-42877 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