CWE-650 Trusting HTTP Permission Methods on the Server Side

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.

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.

• Access Control: Gain Privileges or Assume Identity — An attacker could escalate privileges. • Integrity: Modify Application Data — This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state. • Confidentiality: Read Application Data — An attacker could obtain sensitive information.

• [Architecture and Design, Implementation] 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. • [System Configuration] Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.