dbcve.org
Netweaver Application Server AbapApplication · Sap

CVE-2024-41732

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
SAP NetWeaver Application Server ABAP allows an unauthenticated attacker to craft a URL link that could bypass allowlist controls. Depending on the web applications provided by this server, the attacker might inject CSS code or links into the web application that could allow the attacker to read or modify information. There is no impact on availability of 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 confidence

SAP NetWeaver Application Server ABAP contains an allowlist bypass vulnerability where unauthenticated attackers can craft malicious URLs to bypass allowlist controls. This enables injection of CSS code or arbitrary links into web applications, potentially allowing unauthorized read or modification of information. The attack does not impact system availability.

MitigationApply SAP Security Note addressing the allowlist bypass vulnerability in NetWeaver AS ABAP. Review and validate web application URL handling to ensure allowlist controls properly prevent injection of unauthorized CSS or links.

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
Netweaver Application Server AbapApplication
Affected:= 755= 756= 757= 758= sap_basis_700= sap_basis_701= sap_basis_702= sap_basis_731= sap_basis_912= sap_ui_754

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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 installed NetWeaver AS ABAP version
    Execute transaction code SM51 in the SAP system to view the release and version information of the application server. Alternatively, check the SAP System Information via the SAP Management Console or use transaction code "SAP System" → About to display installed product versions.
    Affected if The displayed version matches any of the following: 755, 756, 757, or 758.
  2. Check SAP Basis component version
    Execute transaction code SPAM (Support Package Manager) or use transaction code SM37 to view installed Support Packages. Navigate to the Installed Software component version information, or use transaction code "System" → Status to display the SAP_Basis component version.
    Affected if The SAP_Basis component version matches any of the following: 700, 701, 702, 731, 912.
  3. Verify SAP_UI component version
    Execute transaction code SE11 or use transaction code SPAM to view the installed SAP_UI component version. Alternatively, check via transaction code "System" → Status → SAP System Information to locate the SAP_UI version.
    Affected if The SAP_UI component version is 754.
  4. Confirm web application exposure
    Execute transaction code SICF (Internet Communication Framework) to view active ICF services. Check if HTTP or HTTPS services are active on the SAP system by reviewing the ICF service tree and noting any publicly accessible web application endpoints.
    Affected if Any ICF services related to web applications (such as BSP applications, Web Dynpro ABAP, or SAP Gateway OData services) are active and accessible via HTTP/HTTPS.
  5. Review allowlist configuration
    Execute transaction code SE80 or navigate to the SAP NetWeaver Administrator. Locate the allowlist configuration for web URL handling, typically found in the security settings or URL filter configuration areas. Inspect the list of allowed URLs and domains.
    Affected if Allowlist controls are configured and active for web applications, but the system is on an affected version (755-758 or sap_basis/sap_ui versions listed above).

The system is affected if it runs any of the specified versions (755, 756, 757, 758 or sap_basis versions 700-702/731/912 or sap_ui 754) AND has web applications accessible via HTTP/HTTPS with allowlist controls enabled.

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

Apply SAP Security Note addressing the allowlist bypass vulnerability in NetWeaver AS ABAP. Review and validate web application URL handling to ensure allowlist controls properly prevent injection of unauthorized CSS or links.

Fix this in Netweaver Application Server Abap 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-41732 — 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-41732 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