CVE-2013-6822
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 · uneditedGRMGApp in SAP NetWeaver allows remote attackers to have unspecified impact and attack 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 · moderate confidenceGRMGApp in SAP NetWeaver contains an XML External Entity (XXE) vulnerability that allows remote attackers to inject malicious external entity references into XML processing, potentially enabling disclosure of internal files, SSRF attacks, or denial of service via specially crafted XML requests.
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 dataall versionsCVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Identify GRMGApp deployment statusCheck if the GRMGApp (Guided Reporting Message Generator Application) is deployed on your SAP NetWeaver system. This is typically found in the SAP NetWeaver Application Server Java under the web container or via transaction code SE80 in the BSP application repository.Affected if GRMGApp is actively deployed and accessible on the system
-
Determine SAP NetWeaver versionOn the SAP system, use transaction code SMINFO or check the SAP System Information under System -> Status in the SAP GUI to retrieve the NetWeaver version and patch level.Affected if Any version of SAP NetWeaver is installed, as all versions are affected according to the CVE advisory
-
Inspect XML parser configuration for external entity settingsExamine the XML parser configuration used by GRMGApp. This typically involves reviewing the parser settings in the application server configuration files or the web.xml deployment descriptor for the GRMGApp application to check if external entity processing is enabled.Affected if The XML parser is configured to allow external entity resolution (DTD processing enabled)
-
Test for XXE vulnerability via crafted XML requestIf GRMGApp is accessible, send a test XML request containing an external entity reference (such as a DOCTYPE with an external entity pointing to a local file or internal URL) to the GRMGApp endpoint and observe if the parser processes the external reference.Affected if The GRMGApp endpoint processes XML with external entities without rejecting or neutralizing them
You are affected if GRMGApp is deployed on your SAP NetWeaver system and the XML parser configuration permits external entity processing in XML requests.
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 SAP security patches for CVE-2013-6822; if patches unavailable, disable XML external entity processing in the XML parser configuration for GRMGApp or implement input validation to reject XML containing DTD declarations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6822 — 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-6822 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