CVE-2025-23186
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 · uneditedIn certain conditions, SAP NetWeaver Application Server ABAP allows an authenticated attacker to craft a Remote Function Call (RFC) request to restricted destinations, which can be used to expose credentials for a remote service. These credentials can then be further exploited to completely compromise the remote service, potentially resulting in a significant impact on the 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 NetWeaver AS ABAP contains an authorization flaw allowing authenticated attackers to bypass restrictions on RFC destinations and extract stored credentials. These credentials can then be used to fully compromise the connected remote service, affecting all three CIA pillars.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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.
-
Identify SAP NetWeaver ABAP systemExecute transaction SM37 or check system version via SAP system information (transaction SAINT or SPAM). Confirm the system is running SAP NetWeaver AS ABAP.Affected if The system is SAP NetWeaver AS ABAP and an attacker with any authenticated RFC access exists.
-
Check for configured RFC destinationsExecute transaction SM59 to view RFC destinations. Examine all RFC destinations of type 3 (ABAP system), G (ABAP program), H (HTTP connection to ABAP), and T (TCP/IP).Affected if Any RFC destination exists in the system, regardless of type.
-
Verify stored credentials in RFC destinationsIn SM59, inspect each RFC destination for stored logon credentials in the Logon/Security tab. Check for entries in fields for user and password that are pre-populated rather than using current user logon.Affected if RFC destinations contain saved user credentials instead of using current user authentication.
-
Review authorization roles for RFC accessExecute transaction PFCG to examine roles assigned to users. Check for roles containing authorization objects S_RFC and S_BDS_RFC. Look for excessive RFC authorization grants (such as full access to function modules like RFC_READ_TABLE).Affected if Users have broad RFC authorization grants that bypass intended restrictions.
-
Examine system logs for RFC credential extractionExecute transaction SLG1 (or use RSLOGPRF) to review security audit logs and system logs for entries indicating unauthorized access to RFC destination credentials or unusual RFC_READ_TABLE calls.Affected if Logs show unauthorized RFC destination access or credential retrieval attempts by low-privilege users.
A user is affected if they run SAP NetWeaver AS ABAP with any configured RFC destinations that store credentials, especially if low-privilege authenticated users can access RFC destination configurations.
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 dataRestrict RFC destination access through proper authorization checks, apply relevant SAP security notes, and rotate exposed credentials immediately.
- Consultation6.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,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23186 — 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-23186 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