背景の詳細
導入モード
Architecture and Design
Implementation
適用可能なプラットフォーム
言語
クラス: Not Language-Specific (Undetermined)
テクノロジー
クラス: Web Based (Often)
名前: Web Server (Undetermined)
一般的な結果
| スコープ |
影響 |
可能性 |
| Confidentiality | Read Application Data | |
観察された例
| 参考文献 |
説明 |
| Security camera includes a password in its query string |
| ML/NLP-based automation product calls a GET method with sensitive information in the query string. |
| Web-based communication product includes an access token in the query string of a GET request |
| A discussion platform leaks private information in GET requests. |
潜在的な緩和策
Phases : Implementation
When sending sensitive information, only
include it in the request body or request headers
instead of the query string. This may require avoiding
use of GET requests.
検出方法
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有効性 : High
脆弱性マッピングノート
理由 : 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.
参考文献
REF-1512
Information exposure through query strings in URL
OWASP.
https://owasp.org/www-community/vulnerabilities/Information_exposure_through_query_strings_in_url
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
Version |
| CWE Community |
|
2006-12-15 +00:00 |
2006-12-15 +00:00 |
Draft 5 |
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Potential_Mitigations, Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Relationships, Other_Notes |
| CWE Content Team |
MITRE |
2009-03-10 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2011-03-29 +00:00 |
updated Name |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences, Other_Notes |
| 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, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Description, Name, Potential_Mitigations, Relationships |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Description |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Detection_Factors, Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Observed_Examples |
| CWE Content Team |
MITRE |
2025-04-03 +00:00 |
updated Description, Diagram, Other_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Applicable_Platforms, Background_Details, Common_Consequences, Other_Notes, References, Relationships, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-04-30 +00:00 |
updated Background_Details, Description, Name, Observed_Examples, Potential_Mitigations |