| Name |
HTTP Verb Tampering |
|
| Likelyhood of attack |
Typical severity |
| Medium |
Medium |
|
| Summary |
An attacker modifies the HTTP Verb (e.g. GET, PUT, TRACE, etc.) in order to bypass access restrictions. Some web environments allow administrators to restrict access based on the HTTP Verb used with requests. However, attackers can often provide a different HTTP Verb, or even provide a random string as a verb in order to bypass these protections. This allows the attacker to access data that should otherwise be protected. |
| Prerequisites |
The targeted system must attempt to filter access based on the HTTP verb used in requests. |
| Solutions | Design: Ensure that only legitimate HTTP verbs are allowed. Design: Do not use HTTP verbs as factors in access decisions. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-302 |
Authentication Bypass by Assumed-Immutable Data |
| CWE-654 |
Reliance on a Single Factor in a Security Decision |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-220 |
An adversary takes advantage of weaknesses in the protocol by which a client and server are communicating to perform unexpected actions. Communication protocols are necessary to transfer messages between client and server applications. Moreover, different protocols may be used for different types of interactions. |
|