Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Opis

The Secure attribute for sensitive cookies in HTTPS sessions is not set.

Skutki

• Confidentiality

  Read Application Data

  Omitting the secure flag makes it possible for the user agent to send the cookies in plaintext over an HTTP session.

Zapobieganie

• Implementation

  Always set the secure attribute when the cookie should be sent via HTTPS only.

Przykłady podatności

• CVE-2024-47833 python library for ML and data science does not use the Secure flag for session cookies
• CVE-2004-0462 A product does not set the Secure attribute for sensitive cookies in HTTPS sessions, which could cause the user agent to send those cookies in plaintext over an HTTP session with the product.
• CVE-2008-3663 A product does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.
• CVE-2008-3662 A product does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.
• CVE-2008-0128 A product does not set the secure flag for a cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.

Słabość nadrzędna

• CWE-319 Cleartext Transmission of Sensitive Information

Kiedy powstaje

• Implementation

Dotyczy

Web Based