dbcve.org
Application Interface FrameworkApplication · Sap

CVE-2024-21737

CRITICAL · 9.1 CVSS v3.1 Published 2024-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
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 Application Interface Framework File Adapter - version 702, a high privilege user can use a function module to traverse through various layers and execute OS commands directly. By this, such user can control the behaviour of the application. This leads to considerable impact on confidentiality, integrity and availability.

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 Application Interface Framework File Adapter version 702, an OS command injection vulnerability exists where high-privilege users can abuse a function module to traverse system layers and execute operating system commands directly, giving attackers full control over application behavior.

MitigationRestrict privileged access to the affected function module, apply SAP security patches for CVE-2024-21737, and implement least-privilege authorization controls on sensitive function modules.

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
Application Interface FrameworkApplication
Affected:= 702

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

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

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

  1. Identify SAP Application Interface Framework installation and version
    Using SAP transaction SE11 or SM37, query the SAP AIF component version. Alternatively, check via SAP MTR (Maintenance Transaction Router) or SAP Solution Manager by viewing the installed software components for SAP AIF. The version will be displayed in the component details.
    Affected if The installed version of SAP Application Interface Framework equals exactly 702 (version 702)
  2. Confirm File Adapter component is present
    Check the SAP AIF configuration via transaction SA38 or by viewing the installed AIF add-on components. Look for File Adapter or message monitoring components that are part of the AIF infrastructure.
    Affected if File Adapter component is installed as part of the AIF 702 installation
  3. Locate the vulnerable function module
    Using SAP transaction SE37 (Function Builder) or SE84, search for function modules related to file operations within the AIF File Adapter namespace. The vulnerability exists in a function module that handles file processing and allows command execution.
    Affected if A function module related to file processing in AIF File Adapter is accessible and present in the system
  4. Verify if high-privilege access exists to the function module
    Using SAP transaction SUIM (User Information System) or PFCG, check which users or roles have authorization for the vulnerable function module. Also verify via transaction SU53 after attempted access to see authorization missing messages.
    Affected if Users with elevated privileges (such as SAP_ALL, or specific AIF administrator roles) have access to the function module

A system is affected if SAP Application Interface Framework version 702 is installed with the File Adapter component and the vulnerable function module is accessible to high-privilege users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict privileged access to the affected function module, apply SAP security patches for CVE-2024-21737, and implement least-privilege authorization controls on sensitive function modules.

Fix this in Application Interface Framework Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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