Issue Details
XML External Entities (XXE)
Aliases: None
Explanation
In OWASP 2017, A4 XML External Entities (XXE) combines related risk themes across XML External Entities (XXE), Insecure Design. XXE abuses XML parsers to access local files, trigger SSRF, or leak internal data. Insecure design reflects missing security controls in architecture and workflows before implementation. These weaknesses are often exploited as a chain: attackers start with weak input or trust boundaries, pivot through authorization or session gaps, and then move toward data exposure, integrity loss, or service disruption. Operationally, this can increase incident frequency, enlarge blast radius, and raise both remediation cost and compliance exposure when controls are missing or inconsistently enforced across services.
Remedy
For OWASP 2017 A4 XML External Entities (XXE), apply defense in depth across design, implementation, deployment, and operations rather than relying on a single control. Priority controls include: Disable external entity resolution in XML parsers and use hardened parser configurations by default. Perform threat modeling early, add abuse-case testing, and build security controls into architecture decisions. Treat mitigation as a continuous program: define security requirements up front, enforce them in CI/CD gates, and verify effectiveness with threat modeling, code review, automated testing, and recurring penetration testing. Add monitoring and incident-response readiness so misconfigurations, abuse patterns, and control regressions are detected early and corrected before they become repeatable attack paths.
| Year | Rank | Category |
|---|---|---|
| 2017 | #4 | A4 - XML External Entities (XXE) |
| 2021 | #5 | A05 - Security Misconfiguration |