1.4 KiB
1.4 KiB
| stage | group | info |
|---|---|---|
| Secure | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments |
Sensitive cookie without Secure attribute
Description
The cookie was transmitted in a Set-Cookie response without the Secure attribute set.
To prevent sensitive cookie values being accidentally transmitted over clear-text HTTP we
recommended that cookies are declared with the Secure attribute.
Remediation
Most web application frameworks allow configuring how cookies are sent to user agents. Consult your framework's documentation for more information on how to enable various security attributes when assigning cookies to clients.
If the application is assigning cookies via writing to the response headers directly, ensure all responses include
the Secure attribute. By enabling this protection, the application will no longer send sensitive cookies over
HTTP.
Example:
Set-Cookie: {cookie_name}=<random secure value>; Secure
Details
| ID | Aggregated | CWE | Type | Risk |
|---|---|---|---|---|
| 614.1 | false | 614 | Passive | Low |