Use of GET request method with sensitive query strings (Authorization header details)
Description
The authorization header value was identified in the request URL. These headers typically contain usernames and passwords or JWT tokens. These values should never be sent in GET requests as they maybe captured by proxy systems, stored in browser history, or stored in log files. If an attacker were to get access to these logs or logging systems, they would be able to gain access to the target account.
Remediation
Authorization header details should never be sent in GET requests. When transmitting sensitive information
such as JWT tokens, always use POST
requests or headers to transmit the sensitive data.
Details
ID | Aggregated | CWE | Type | Risk |
---|---|---|---|---|
598.3 | true | 598 | Passive | Medium |
Links
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support