Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-614 Variante Brouillon
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure' attribute on those cookies.
Définition
What is CWE-614?
This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure' attribute on those cookies.
When a cookie is marked with the 'Secure' attribute, browsers guarantee it will only be sent over encrypted HTTPS connections. If this attribute is missing, even if the application initially uses HTTPS, the browser may inadvertently send the sensitive cookie over an unencrypted HTTP request. This often happens during redirects, when loading mixed content, or if a user manually types an HTTP URL, exposing session tokens or authentication data to interception.
To prevent this, developers must explicitly set the 'Secure' flag for all cookies containing sensitive information in their application code. This is a critical server-side configuration that should be part of a standard secure cookie policy, alongside other attributes like 'HttpOnly' and 'SameSite'. Relying solely on HTTPS for the initial transmission is not sufficient; the 'Secure' attribute provides an essential enforcement layer at the browser level.
Impact réel
Real-world CVEs caused by CWE-614
-
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.
-
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.
-
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.
-
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.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
- 2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
- 3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
- 4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.
Exemple de code vulnérable
Vulnerable Java
The snippet of code below, taken from a servlet doPost() method, sets an accountID cookie (sensitive) without calling setSecure(true).
Cookie c = new Cookie(ACCOUNT_ID, acctID);
response.addCookie(c); Exemple de code sécurisé
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention
How to prevent CWE-614
- Implementation Always set the secure attribute when the cookie should be sent via HTTPS only.
Signaux de détection
How to detect CWE-614
CWE-614
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Questions fréquentes Qu'est-ce que CWE-614 ?
Quelle est la gravité de CWE-614 ?
Quels langages ou plateformes sont affectés par CWE-614 ?
Comment puis-je prévenir CWE-614 ?
Comment Plexicus détecte et corrige CWE-614 ?
Où puis-je en savoir plus sur CWE-614 ?
Frequently asked questions
Qu'est-ce que CWE-614 ?
This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure' attribute on those cookies.
Quelle est la gravité de CWE-614 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-614 ?
MITRE lists the following affected platforms: Web Based.
Comment puis-je prévenir CWE-614 ?
Always set the secure attribute when the cookie should be sent via HTTPS only.
Comment Plexicus détecte et corrige CWE-614 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-614 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-614 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/614.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-614
CWE-319 Parent
Cleartext Transmission of Sensitive Information
This vulnerability occurs when an application sends sensitive data, such as passwords or personal information, over a network connection…
CWE-1428 Frère
Reliance on HTTP instead of HTTPS
This vulnerability occurs when an application uses unencrypted HTTP connections instead of the secure HTTPS alternative, even when HTTPS…
CWE-5 Frère
J2EE Misconfiguration: Data Transmission Without Encryption
This vulnerability occurs when a J2EE application transmits sensitive data, like login credentials or session tokens, across a network…
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.