dbcve.org
Netweaver AbapApplication · Sap

CVE-2015-1309

MEDIUM · 5.0 CVSS v2.0 Published 2015-01-22
Fix available
A fix is available. Upgrade to after 7.31 or later.
See remediation →
59/100
Remediation priority · Elevated
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
XML external entity vulnerability in the Extended Computer Aided Test Tool (eCATT) in SAP NetWeaver AS ABAP 7.31 and earlier allows remote attackers to access arbitrary files via a crafted XML request, related to ECATT_DISPLAY_XMLSTRING_REMOTE, aka SAP Note 2016638.

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's eCATT (Extended Computer Aided Test Tool) component within NetWeaver AS ABAP 7.31 and earlier. The flaw in function module ECATT_DISPLAY_XMLSTRING_REMOTE allows remote attackers to craft malicious XML requests that reference external entities, enabling arbitrary file system access on the affected server.

MitigationApply SAP Note 2016638 to patch the vulnerability in the ECATT_DISPLAY_XMLSTRING_REMOTE function module, and consider disabling eCATT if not required in production environments as a defense-in-depth measure.

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 AbapApplication
Affected:<= 7.31

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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. Verify SAP NetWeaver ABAP version
    Execute transaction SM37 or use ABAP report RS_VERSION to check the SAP_BASIS version. Look for a version number of 7.31 or lower in the format such as 7.00, 7.01, 7.02, 7.10, 7.20, 7.30, or 7.31.
    Affected if The installed SAP_BASIS version is 7.31 or any version number lower than 7.31 (for example 7.00, 7.10, 7.20, 7.30).
  2. Confirm eCATT is enabled
    Execute transaction SECATT to access the eCATT configuration. Alternatively, query table T000 for client configuration entries related to eCATT (check for profile parameter ecatt/enable or similar).
    Affected if eCATT (Extended Computer Aided Test Tool) is enabled and accessible via transaction SECATT or ECATT.
  3. Check function module ECATT_DISPLAY_XMLSTRING_REMOTE existence
    Execute transaction SE37 and enter function module name ECATT_DISPLAY_XMLSTRING_REMOTE. Check if the module exists and is actively maintained.
    Affected if The function module ECATT_DISPLAY_XMLSTRING_REMOTE exists in the system and is available for remote calls.
  4. Verify remote-enabled function module access
    Use transaction SM37 to monitor RFC-enabled function calls, or check transaction SU01 for users authorized to call ECATT_DISPLAY_XMLSTRING_REMOTE via RFC. Review the function module's attributes in SE37 to confirm it is marked as remote-enabled (RFC).
    Affected if The function module is remote-enabled and can be invoked via RFC without additional restrictions.
  5. Inspect recent eCATT execution logs
    Execute transaction SCOT or check system log via transaction SM37 to look for recent executions of eCATT-related function modules. Use transaction SLG1 to review application logs related to ECATT_DISPLAY_XMLSTRING_REMOTE.
    Affected if There are recent executions of eCATT or the vulnerable function module in the system logs.

The environment is affected if SAP NetWeaver ABAP version is 7.31 or lower AND eCATT is enabled AND the function module ECATT_DISPLAY_XMLSTRING_REMOTE is accessible as a remote-enabled function module.

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
Upgrade available Upgrade to a release after 7.31
Interim mitigation

Apply SAP Note 2016638 to patch the vulnerability in the ECATT_DISPLAY_XMLSTRING_REMOTE function module, and consider disabling eCATT if not required in production environments as a defense-in-depth measure.

Fix this in Netweaver Abap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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