Description
The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state.
The HTTP GET method and some other methods are designed to retrieve resources and not to alter the state of the application or resources on the server side. Furthermore, the HTTP specification requires that GET requests (and other requests) should not have side effects. Believing that it will be enough to prevent unintended resource alterations, an application may disallow the HTTP requests to perform DELETE, PUT and POST operations on the resource representation. However, there is nothing in the HTTP protocol itself that actually prevents the HTTP GET method from performing more than just query of the data. Developers can easily code programs that accept a HTTP GET request that do in fact create, update or delete data on the server. For instance, it is a common practice with REST based Web Services to have HTTP GET requests modifying resources on the server side. However, whenever that happens, the access control needs to be properly enforced in the application. No assumptions should be made that only HTTP DELETE, PUT, POST, and other methods have the power to alter the representation of the resource being accessed in the request.
Potential Impact
Access Control
Gain Privileges or Assume Identity
Integrity
Modify Application Data
Confidentiality
Read Application Data
Mitigations & Prevention
Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.
Related Weaknesses
Frequently Asked Questions
What is CWE-650?
CWE-650 (Trusting HTTP Permission Methods on the Server Side) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass inte...
How can CWE-650 be exploited?
Attackers can exploit CWE-650 (Trusting HTTP Permission Methods on the Server Side) to gain privileges or assume identity. This weakness is typically introduced during the Architecture and Design, Implementation, Operation phase of software development.
How do I prevent CWE-650?
Key mitigations include: Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.
What is the severity of CWE-650?
CWE-650 is classified as a Variant-level weakness (Low-Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.