1433
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.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 436 Interpretation Conflict 1057
Applicable Platforms
Language : Not Language-Specific (Prevalence = Undetermined)
Likelihood Of Exploit
High
Common Consequences
Scope Impact Likelihood
Access Control Gain Privileges or Assume Identity
An attacker could escalate privileges.
Integrity Modify Application Data
An attacker could modify resources.
Confidentiality Read Application Data
An attacker could obtain sensitive information.
Potential Mitigations
Phase: System Configuration
Configure ACLs on the server side to ensure that proper level of access control is defined for
each accessible resource representation.
MemberOf Relationships
This MemberOf relationships table shows additional CWE Catgeories and Views that reference this
weakness as a member. This information is often useful in understanding where a weakness fits
within the context of external information sources.
Nature Type ID Name Page
MemberOf 945 SFP Secondary Cluster: Insecure Resource Access 888 2394
MemberOf 1348 OWASP Top Ten 2021 Category A04:2021 - Insecure
Design
1344 2491
MemberOf 1398 Comprehensive Categorization: Component Interaction 1400 2524
CWE-651: Exposure of WSDL File Containing Sensitive Information
CWE Version 4.14
CWE-651: Exposure of WSDL File Containing Sensitive Information
CWE-651: Exposure of WSDL File Containing Sensitive Information