dbcve.org
Abap PlatformApplication · Sap

CVE-2024-22131

HIGH · 7.2 CVSS v3.1 Published 2024-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
In SAP ABA (Application Basis) - versions 700, 701, 702, 731, 740, 750, 751, 752, 75C, 75I, an attacker authenticated as a user with a remote execution authorization can use a vulnerable interface. This allows the attacker to use the interface to invoke an application function to perform actions which they would not normally be permitted to perform.  Depending on the function executed, the attack can read or modify any user/business data and can make the entire system unavailable.

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 confidence

In SAP ABA (Application Basis), an authenticated user with remote execution authorization can exploit a vulnerable interface to invoke application functions beyond their intended permissions, achieving privilege escalation. This allows arbitrary function execution leading to unauthorized read/write access to any user/business data or complete system unavailability.

MitigationRestrict and validate the remote execution interface authorization checks to ensure only permitted functions can be invoked, and review user roles to limit remote execution authorization to only essential personnel.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Abap PlatformApplication
Affected:= 75c= 75i= 700= 701= 702= 731= 740= 750= 751= 752

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 checks

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

  1. Identify your SAP ABAP Platform version
    Use transaction SM51 to view the installed SAP release version, or check the SAP System Landscape Directory (SLD). Compare the version number to the affected list: 75c, 75i, 700, 701, 702, 731, 740, 750, 751, 752.
    Affected if Your installed version matches one of the affected versions listed.
  2. Determine if remote execution interface is active
    Review your SAP system configuration to check whether remote-enabled function modules or the remote execution interface is configured. Use transaction SM59 to view RFC destinations and verify if remote call capabilities are enabled for ABAP applications.
    Affected if Remote execution interface or remote-enabled RFC destinations are configured and active in your system.
  3. Audit user roles with remote execution authorization
    Use transaction PFCG or SUIM to review roles assigned to users. Filter for roles that include authorization objects related to remote execution (such as S_RFC or access to remote-enabled function groups). Identify users who have been granted remote execution privileges.
    Affected if Users exist in your system who have remote execution authorization roles assigned.
  4. Verify authorization checks on remote-capable function modules
    Review the ABAP code or configuration of your remote execution interface to determine if proper authorization checks are implemented before allowing function module invocation. Check whether the interface enforces permission validation for the specific functions being called.
    Affected if The remote execution interface lacks proper authorization validation or allows invocation of functions beyond the caller's intended permissions.

You are affected if your SAP ABAP Platform version matches one of the affected versions AND remote execution interface is active with users possessing remote execution authorization privileges.

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

Restrict and validate the remote execution interface authorization checks to ensure only permitted functions can be invoked, and review user roles to limit remote execution authorization to only essential personnel.

Recommended fix Moderate confidence
  1. 1. Access the SAP Support Portal at support.sap.com and search for the relevant security patch note for CVE-2024-22131
  2. 2. Apply the SAP Security Note associated with this CVE to your affected SAP ABA (Application Basis) installation
  3. 3. After applying the patch, verify the fix by checking that the vulnerable interface no longer allows unauthorized function invocation
  4. 4. Review and restrict the remote execution authorization permissions for users who do not require this capability
  5. 5. Conduct security testing to confirm the vulnerability has been mitigated

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

Fix this in Abap Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22131 — 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-2024-22131 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