dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2024-24743

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
SAP NetWeaver AS Java (CAF - Guided Procedures) - version 7.50, allows an unauthenticated attacker to submit a malicious request with a crafted XML file over the network, which when parsed will enable him to access sensitive files and data but not modify them. There are expansion limits in place so that availability is not affected.

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

This is an XML External Entity (XXE) injection vulnerability in SAP NetWeaver AS Java CAF Guided Procedures version 7.50. An unauthenticated attacker can submit crafted XML requests over the network that, when parsed by the vulnerable component, allows reading sensitive files from the server file system. The attacker gains read-only access to sensitive data without the ability to modify files or affect availability due to expansion limits in place.

MitigationApply the relevant SAP Security Note to patch the vulnerable CAF Guided Procedures component and disable external entity processing in XML parsers. Additionally, restrict network access to the affected SAP NetWeaver Java services and implement WAF rules to detect XXE payloads.

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 JavaApplication
Affected:= 7.50

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 SAP NetWeaver AS Java version
    Access the SAP NetWeaver Administrator (NWA) or use SAP LMND (Landscape, Network, Directory) to check the installed version. Alternatively, check the JAR file version in the /usr/sap/<SID>/<instance>/j2ee/cluster/ directory or query the SAP MII version via the SAP System Information service.
    Affected if The installed version is exactly 7.50 (Build ID matching 7.50)
  2. Verify CAF Guided Procedures component is deployed
    Check if the Composite Application Framework (CAF) Guided Procedures application is running in the SAP J2EE Engine. In the SAP Administrator, navigate to Applications and look for 'caf_gp' or 'GuidedProcedures' ear deployment, or query the SAP CAF GP web service endpoint over HTTP/HTTPS.
    Affected if The CAF Guided Procedures application is deployed and running on the affected NetWeaver Java 7.50 system
  3. Confirm network exposure of CAF GP services
    Identify URLs/ports where CAF Guided Procedures SOAP or HTTP endpoints are accessible. Check SAP ICM (Internet Communication Manager) configuration and web dispatcher rules for paths like /CAF GP/ or /sap/bc/rest/ that expose the XML parsing interface.
    Affected if The CAF GP XML service endpoint is exposed to untrusted network segments or the public internet
  4. Review XML parser configuration for external entity processing
    Inspect the SAP J2EE XML parser settings in the SAP NetWeaver Administrator under Server > Services > XML Parser. Check whether the XML parser allows external entity expansion, typically configured in the parser factory settings or in the CAF GP application deployment descriptor (web.xml or application.xml).
    Affected if External entity processing is enabled in the XML parser configuration (DTD external entity support is not disabled)
  5. Analyze server logs for XXE indicators
    Search SAP NetWeaver system logs (default.trc, error.trc) and HTTP access logs for patterns indicating XXE exploitation attempts, such as '<!ENTITY', 'SYSTEM', 'file://', 'php://' or unusual XML payload submissions to CAF GP endpoints.
    Affected if Logs contain XML requests with external entity declarations or unusual file path references to sensitive system files

A system is affected if it runs SAP NetWeaver AS Java version 7.50 with the CAF Guided Procedures component deployed and exposed, with XML parser external entity processing 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 the relevant SAP Security Note to patch the vulnerable CAF Guided Procedures component and disable external entity processing in XML parsers. Additionally, restrict network access to the affected SAP NetWeaver Java services and implement WAF rules to detect XXE payloads.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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