Use of GET request method with sensitive query strings (session ID)

Description

A session ID was identified in the request URL as well as a cookie value. Session IDs should not 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 the session ID they would potentially be able to gain access to the target account.

Remediation

As request headers are rarely logged or captured by third party systems, ensure session ID values are only sent in cookies (assigned via Set-Cookie response headers) and never sent in the request URL.

Details

ID	Aggregated	CWE	Type	Risk
598.1	true	598	Passive	Medium

Help & feedback

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.
Join First Look to help shape new features.

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