CWE-650 詳細

CWE-650

Trusting HTTP Permission Methods on the Server Side
2008-01-30
00h00 +00:00
高
Incomplete
2026-10-28
00h00 +00:00
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
通知を管理する

名前: 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.

CWE の説明

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.

一般情報

背景の詳細

導入モード

Array : Developers can easily code programs that accept a HTTP GET request that 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.
Operation

適用可能なプラットフォーム

言語

クラス: Not Language-Specific (Undetermined)

テクノロジー

クラス: Web Based (Undetermined)
名前: Web Server (Undetermined)

一般的な結果

スコープ 影響 可能性
Access ControlGain Privileges or Assume Identity

注記:An attacker could escalate privileges.
IntegrityModify 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.
ConfidentialityRead Application Data

注記:An attacker could obtain sensitive information.

潜在的な緩和策

Phases : 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.
Phases : System Configuration
Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.

脆弱性マッピングノート

理由 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
コメント : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

登録情報

名前 組織 日付 リリース日 Version
Evgeny Lebanidze Cigital 2008-01-30 +00:00 2008-01-30 +00:00 Draft 8

変更履歴

名前 組織 日付 コメント
CWE Content Team MITRE 2008-09-08 +00:00 updated Common_Consequences, Relationships
CWE Content Team MITRE 2008-10-14 +00:00 updated Description, Enabling_Factors_for_Exploitation
CWE Content Team MITRE 2009-10-29 +00:00 updated Common_Consequences
CWE Content Team MITRE 2011-03-29 +00:00 updated Common_Consequences
CWE Content Team MITRE 2011-06-01 +00:00 updated Common_Consequences
CWE Content Team MITRE 2012-05-11 +00:00 updated Relationships
CWE Content Team MITRE 2012-10-30 +00:00 updated Potential_Mitigations
CWE Content Team MITRE 2014-07-30 +00:00 updated Relationships
CWE Content Team MITRE 2017-01-19 +00:00 updated Relationships
CWE Content Team MITRE 2017-11-08 +00:00 updated Applicable_Platforms, Description, Enabling_Factors_for_Exploitation, Observed_Examples, Relationships
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2021-10-28 +00:00 updated Relationships
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Background_Details, Common_Consequences, Description, Modes_of_Introduction, Potential_Mitigations, Time_of_Introduction