CVE-2013-6815
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 · uneditedThe SHSTI_UPLOAD_XML function in the Application Server for ABAP (AS ABAP) in SAP NetWeaver 7.31 and earlier allows remote attackers to cause a denial of service via unspecified vectors, related to an XML External Entity (XXE) issue.
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 confidenceThis is an XML External Entity (XXE) vulnerability in SAP NetWeaver's Application Server for ABAP (AS ABAP). The SHSTI_UPLOAD_XML function processes XML uploads without properly restricting external entity expansion, allowing remote attackers to cause denial of service via malicious XML payloads that trigger excessive resource consumption or parsing errors.
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<= 7.31= 4.0= 6.4= 7.0= 7.01= 7.02= 7.03= 7.10= 7.30CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Check SAP NetWeaver AS ABAP versionExecute transaction code 'SM51' or use transaction 'SUSR' to view system version information. Navigate to the system information screen to display the SAP NetWeaver release and support package level.Affected if The installed version matches <= 7.31, or equals 4.0, 6.4, 7.0, 7.01, 7.02, 7.03, 7.10, or 7.30 from the affected versions list.
-
Locate the SHSTI_UPLOAD_XML function moduleExecute transaction code 'SE37' (Function Builder) and search for function module name 'SHSTI_UPLOAD_XML'. Check if the function module exists in the system.Affected if The function module SHSTI_UPLOAD_XML exists in the SAP system.
-
Verify function module accessibilityIn transaction 'SE37', display the function module details. Check the 'Attributes' tab to see if the function is marked as 'RFC enabled' or 'remote-enabled', and review any released status.Affected if The function module is released for external access or RFC calls.
-
Check for recent usage or logs of the functionExecute transaction code 'ST03N' (Performance - Workload) or review transaction 'SLG1' (Application Log) for entries related to SHSTI_UPLOAD_XML function calls.Affected if There are recent log entries or executions of the SHSTI_UPLOAD_XML function in the system.
A system is affected if it runs a vulnerable SAP NetWeaver version (4.0, 6.4, 7.0-7.03, 7.10, 7.30, or <=7.31) AND has the SHSTI_UPLOAD_XML function module accessible for use.
Generated from the published advisory. Verify against your own configuration.
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 dataApply available SAP security notes/patches for this vulnerability. As a compensating control, restrict access to the SHSTI_UPLOAD_XML function to authorized personnel only and implement XML parser hardening to disable external entity processing.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-6815 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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