CAPECattack pattern
CAPEC-250 XML Injection
- Abstraction
- Standard
- Status
- Draft
- Likelihood of attack
- High
- CAPEC version
- 3.9
Description
An attacker utilizes crafted XML user-controllable input to probe, attack, and inject data into the XML database, using techniques similar to SQL injection. The user-controllable input can allow for unauthorized viewing of data, bypassing authentication or the front-end application for direct XML database access, and possibly altering database information.
Execution flow
1. [Explore] [Survey the Target] Using a browser or an automated tool, an adversary records all instances of user-controllable input used to contruct XML queries
2. [Experiment] [Determine the Structure of Queries] Using manual or automated means, test inputs found for XML weaknesses.
3. [Exploit] [Inject Content into XML Queries] Craft malicious content containing XML expressions that is not validated by the application and is executed as part of the XML queries.
Prerequisites
• XML queries used to process user input and retrieve information stored in XML documents
• User-controllable input not properly sanitized
Skills required
• [Low] An attacker must have knowledge of XML syntax and constructs in order to successfully leverage XML Injection
Consequences
• Confidentiality, Access Control, Authorization: Gain Privileges
• Confidentiality: Read Data
Mitigations
• Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as content that can be interpreted in the context of an XML data or a query.
• Use of custom error pages - Attackers can glean information about the nature of queries from descriptive error messages. Input validation must be coupled with customized error pages that inform about an error without disclosing information about the database or application.
Related
Child of · CAPEC (1)
- CAPEC-248 Command Injection attack pattern