Use of GET Request Method With Sensitive Query Strings
Draft Variant
Structure: Simple
Description
The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.
Common Consequences 1
Scope: Confidentiality
Impact: Read Application Data
At a minimum, attackers can garner information from query strings that can be utilized in escalating their method of attack, such as information about the internal workings of the application or database column names. Successful exploitation of query string parameter vulnerabilities could lead to an attacker impersonating a legitimate user, obtaining proprietary data, or simply executing actions not intended by the application developers.
Detection Methods 1
Automated Static AnalysisHigh
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.)Potential Mitigations 1
Phase: Implementation
When sensitive information is sent, use the POST method (e.g. registration form).
Observed Examples 1
CVE-2022-23546A discussion platform leaks private information in GET requests.
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
Taxonomy Mapping
- Software Fault Patterns
Notes
OtherThe query string for the URL could be saved in the browser's history, passed through Referers to other web sites, stored in web logs, or otherwise recorded in other sources. If the query string contains sensitive information such as session identifiers, then attackers can use this information to launch further attacks.