CVE-2025-42875
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 · uneditedThe SAP Internet Communication Framework does not conduct any authentication checks for features that need user identification allowing an attacker to reuse authorization tokens, violating secure authentication practices causing low impact on Confidentiality, Integrity and Availability 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 · moderate confidenceSAP Internet Communication Framework lacks proper authentication checks for features requiring user identification, allowing attackers to reuse authorization tokens and bypass secure authentication practices.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
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 ICF is activeExecute transaction SICF in SAP GUI and check if any ICF services are active and exposed. Use transaction SMICM to verify the ICM (Internet Communication Manager) is running and ICF is enabled.Affected if ICF services are active and accessible without proper authentication controls enforced at the service level.
-
Identify exposed ICF endpointsReview transaction SICF for publicly accessible ICF services. Check the 'Handler List' for each active service to identify if custom handlers bypass standard authentication.Affected if ICF services with URL exposure have handlers that do not enforce user authentication or session validation.
-
Check authentication settings on ICF servicesIn transaction SICF, for each relevant ICF service, verify the 'Logon Procedure' setting. Look for services where authentication is set to 'No Logon Required' or uses weak authentication methods.Affected if ICF services require no authentication or use authentication methods that allow token reuse without freshness validation.
-
Review token and session handling configurationCheck profile parameters related to ICF security: icm/HTTP/timeout, icm/authentication, and logon ticket settings via transaction RZ11. Inspect whether token revocation is enforced.Affected if Session tokens or logon tickets can be reused across requests without validation of token freshness or revocation status.
-
Compare installed SAP NetWeaver versionExecute transaction SM37 or check system version via transaction SM51. Compare the version string (e.g., SAP_BASIS release) against known affected SAP NetWeaver versions for CVE-2025-42875.Affected if The installed SAP NetWeaver version falls within the vulnerable version range for this CVE.
The environment is affected if SAP ICF services are active and accessible, and either the system runs a vulnerable SAP NetWeaver version or ICF services lack proper authentication enforcement allowing token reuse.
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 dataImplement proper authentication validation for all user-facing features in the ICF and enforce token freshness/revocation to prevent token reuse attacks.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42875 — 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-42875 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