CAPEC-545: Pull Data from System Resources
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 :
Possibility :
Type :
Standard
Relationships with other CAPECs
This table shows the other attack patterns and high level categories that are related to this attack pattern.
Skills required
This table shows the other attack patterns and high level categories that are related to this attack pattern.
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-1239: Improper Zeroization of Hardware Register
CWE-1243: Sensitive Non-Volatile Information Not Protected During Debug
CWE-1258: Exposure of Sensitive System Information Due to Uncleared Debug Information
CWE-1266: Improper Scrubbing of Sensitive Data from Decommissioned Device
CWE-1272: Sensitive Information Uncleared Before Debug/Power State Transition
CWE-1278: Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
CWE-1323: Improper Management of Sensitive Trace Data
CWE-1330: Remanent Data Readable after Memory Erase
Visit http://capec.mitre.org/ for more details.