This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Information exposure through query strings in url"
(Created page with "{{stub}} {{Template:Vulnerability}} Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' ==Description== Information exposure through query st...") |
m (Removed "Related Attacks" as it's open for debate.) (Tag: Visual edit) |
||
| Line 38: | Line 38: | ||
==Related [[Attacks]]== | ==Related [[Attacks]]== | ||
| − | + | TBD | |
| − | |||
==Related [[Vulnerabilities]]== | ==Related [[Vulnerabilities]]== | ||
| Line 62: | Line 61: | ||
* [https://www.owasp.org/index.php/Top_10_2013-A6-Sensitive_Data_Exposure Top 10 2013-A6-Sensitive Data Exposure] | * [https://www.owasp.org/index.php/Top_10_2013-A6-Sensitive_Data_Exposure Top 10 2013-A6-Sensitive Data Exposure] | ||
* [https://portswigger.net/knowledgebase/issues/details/00400300_passwordsubmittedusinggetmethod Passwords Submitted Using GET Method] | * [https://portswigger.net/knowledgebase/issues/details/00400300_passwordsubmittedusinggetmethod Passwords Submitted Using GET Method] | ||
| − | |||
[[Category:Cryptographic Vulnerability]] | [[Category:Cryptographic Vulnerability]] | ||
Revision as of 20:30, 6 April 2017
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Last revision (mm/dd/yy): 04/6/2017
Description
Information exposure through query strings in GET request is when sensitive data is passed to parameters in the URL. This allows attackers to obtain sensitive data such as usernames, passwords, tokens (authX), database details, and any other potentially sensitive data. Simply using HTTPS does not resolve this vulnerability.
Risk Factors
TBD
Examples
Regardless of using encryption, the following URL will expose information in the locations detailed below: https://vulnerablehost.com/authuser?user=bob&authz_token=1234&expire=1500000000
The parameter values for 'user', 'authz_token', and 'expire' will be exposed in the following locations when using HTTP or HTTPS:
- Referer Header
- Web Logs
- Shared Systems
- Browser History
- Browser Cache
- Shoulder Surfing
- TBD
When not using an encrypted channel, all of the above and the following:
- Man-in-the-Middle
- TBD
Exposure Proof-of-Concept
The following figure displays how an internal attacker can potentially exploit this vulnerability as the request above is captured in the server logs even when requested via an encrypted channel:
Related Attacks
TBD
Related Vulnerabilities
TBD
Related Controls
TBD
Related Technical Impacts
TBD
