XML Injection (aka Blind XPath Injection)| ID: 91 | Date: (C)2012-05-14 (M)2022-10-10 |
| Type: weakness | Status: DRAFT |
| Abstraction Type: Base |
Description
The software does not properly neutralize special elements that
are used in XML, allowing attackers to modify the syntax, content, or commands
of the XML before it is processed by an end system.
Extended DescriptionWithin XML, special elements could include reserved words or characters
such as "<", ">", """, and "&", which could then be used to add
new data or modify XML syntax.
Applicable PlatformsLanguage Class: All
Time Of Introduction
- Architecture and Design
- Implementation
Related Attack Patterns
Common Consequences
| Scope | Technical Impact | Notes |
|---|
| ConfidentialityIntegrityAvailability | Execute unauthorized code or
commandsRead application
dataModify application
data | |
Detection MethodsNone
Potential Mitigations
| Phase | Strategy | Description | Effectiveness | Notes |
|---|
| Implementation | Input Validation | Assume all input is malicious. Use an "accept known good" input
validation strategy, i.e., use a whitelist of acceptable inputs that
strictly conform to specifications. Reject any input that does not
strictly conform to specifications, or transform it into something that
does.When performing input validation, consider all potentially relevant
properties, including length, type of input, the full range of
acceptable values, missing or extra inputs, syntax, consistency across
related fields, and conformance to business rules. As an example of
business rule logic, "boat" may be syntactically valid because it only
contains alphanumeric characters, but it is not valid if the input is
only expected to contain colors such as "red" or "blue."Do not rely exclusively on looking for malicious or malformed inputs
(i.e., do not rely on a blacklist). A blacklist is likely to miss at
least one undesirable input, especially if the code's environment
changes. This can give attackers enough room to bypass the intended
validation. However, blacklists can be useful for detecting potential
attacks or determining which inputs are so malformed that they should be
rejected outright. | | |
Relationships
| Related CWE | Type | View | Chain |
|---|
| CWE-91 ChildOf CWE-896 | Category | CWE-888 | |
Demonstrative ExamplesNone
White Box Definitions None
Black Box Definitions None
Taxynomy Mappings
| Taxynomy | Id | Name | Fit |
|---|
| PLOVER | | XML injection (aka Blind Xpath injection) | |
| OWASP Top Ten 2007 | A2 | Injection Flaws | CWE_More_Specific |
| OWASP Top Ten 2004 | A6 | Injection Flaws | CWE_More_Specific |
| WASC | 23 | XML Injection | |
References:
- Amit Klein .Blind XPath Injection. 2004-05-19.
- Mark Dowd John McDonald Justin Schuh .The Art of Software Security Assessment 1st Edition. Addison Wesley. Section:'Chapter 17, "XML Injection", Page 1069.'. Published on 2006.
