CWE-598: Use of GET Request Method With Sensitive Query Strings

What is Use of GET Request Method With Sensitive Query Strings?

• Overview: Using the HTTP GET method to handle requests that include sensitive information in the query string can expose this data to unauthorized parties, as GET requests are often logged and visible in browser histories and server logs.

• Exploitation Methods:

• Attackers can intercept GET requests and extract sensitive information from query strings using network sniffing tools.
• Malicious users can exploit server logs or browser histories if they have access, as these often store full URLs including query strings.

• Security Impact:

• Direct consequences include unauthorized disclosure of sensitive data such as credentials, personal information, or payment details.
• Potential cascading effects include session hijacking or identity theft if attackers gain access to sensitive session tokens or user information.
• Business impact could involve reputational damage, legal consequences, and financial loss due to data breaches and non-compliance with data protection regulations.

• Prevention Guidelines:

• Use POST requests instead of GET for handling sensitive data to ensure it is not visible in URLs or logs.
• Implement HTTPS to encrypt data in transit, preventing interception by attackers.
• Regularly audit server logs to ensure no sensitive information is inadvertently stored.
• Use security-focused frameworks and tools that enforce secure handling of requests, such as OWASP's Enterprise Security API (ESAPI) for Java.

Corgea can automatically detect and fix Use of GET Request Method With Sensitive Query Strings in your codebase. [Try Corgea free today](https://corgea.app).

Technical Details

Likelihood of Exploit: Not specified

Affected Languages: Not specified

Affected Technologies: Not specified