CAPEC-53: Postfix, Null Terminate, and Backslash
Description
Extended Description
XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
Severity :
High
Possibility :
High
Type :
Detailed
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.
- Null terminators are not properly handled by the filter.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
- Medium An adversary needs to understand alternate encodings, what the filter looks for and the data format acceptable to the target API
Taxonomy mappings
Mappings to ATT&CK, OWASP and other frameworks.
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.
CWE-20: Improper Input Validation
CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CWE-158: Improper Neutralization of Null Byte or NUL Character
CWE-172: Encoding Error
CWE-173: Improper Handling of Alternate Encoding
CWE-697: Incorrect Comparison
CWE-707: Improper Neutralization
Visit http://capec.mitre.org/ for more details.