CAPEC-219: XML Routing Detour Attacks
Description
Extended Description
By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information. In applications that return a stack trace along with the error, this can enumerate the chain of methods that led up to the point where the error was encountered. This can not only reveal the names of the methods (some of which may have known weaknesses) but possibly also the location of class files and libraries as well as parameter values. In some cases, the stack trace might even disclose sensitive configuration or user information.
Severity :
Medium
Possibility :
High
Type :
Standard
Relationships with other CAPECs
This table shows the other attack patterns and high level categories that are related to this attack pattern.
Prerequisites
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- The targeted system must have multiple stages processing of XML content.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Low To inject a bogus node in the XML routing table
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
Resources required
The attacker must be able to insert or compromise a system into the processing path for the transaction.
Related CWE
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.
Visit http://capec.mitre.org/ for more details.