# Complete CWE Entry Example

This page shows a full CWE entry as returned by `fetchCweList()`. Most projects only need `ID`, `Name`, `Description`, and `References.Full_Details`. The other fields are available for advanced use cases.

```json
{
  "ID": "1004",
  "Name": "Sensitive Cookie Without 'HttpOnly' Flag",
  "Abstraction": "Variant",
  "Structure": "Simple",
  "Status": "Incomplete",
  "Description": "The software uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.",
  "Extended_Description": "The HttpOnly flag directs compatible browsers to prevent client-side script from accessing cookies. Including the HttpOnly flag in the Set-Cookie HTTP response header helps mitigate the risk associated with Cross-Site Scripting (XSS) where an attacker's script code might attempt to read the contents of a cookie and exfiltrate information obtained. When set, browsers that support the flag will not reveal the contents of the cookie to a third party via client-side script executed via XSS.",
  "Related_Weaknesses": {
    "Related_Weakness": {
      "Nature": "ChildOf",
      "CWE_ID": "732",
      "View_ID": "1000",
      "Ordinal": "Primary"
    }
  },
  "Applicable_Platforms": {
    "Language": {
      "Class": "Language-Independent",
      "Prevalence": "Undetermined"
    },
    "Technology": {
      "Class": "Web Based",
      "Prevalence": "Undetermined"
    }
  },
  "Background_Details": {
    "Background_Detail": "An HTTP cookie is a small piece of data attributed to a specific website and stored on the user's computer by the user's web browser. This data can be leveraged for a variety of purposes including saving information entered into form fields, recording user activity, and for authentication purposes. Cookies used to save or record information generated by the user are accessed and modified by script code embedded in a web page. While cookies used for authentication are created by the website's server and sent to the user to be attached to future requests. These authentication cookies are often not meant to be accessed by the web page sent to the user, and are instead just supposed to be attached to future requests to verify authentication details."
  },
  "Modes_Of_Introduction": {
    "Introduction": [
      {
        "Phase": "Implementation"
      },
      {
        "Phase": "Architecture and Design"
      }
    ]
  },
  "Likelihood_Of_Exploit": "Medium",
  "Common_Consequences": {
    "Consequence": [
      {
        "Scope": "Confidentiality",
        "Impact": "Read Application Data",
        "Note": "If the HttpOnly flag is not set, then sensitive information stored in the cookie may be exposed to unintended parties."
      },
      {
        "Scope": "Integrity",
        "Impact": "Gain Privileges or Assume Identity",
        "Note": "If the cookie in question is an authentication cookie, then not setting the HttpOnly flag may allow an adversary to steal authentication data (e.g., a session ID) and assume the identity of the user."
      }
    ]
  },
  "Potential_Mitigations": {
    "Mitigation": {
      "Phase": "Implementation",
      "Description": "Leverage the HttpOnly flag when setting a sensitive cookie in a response.",
      "Effectiveness": "High",
      "Effectiveness_Notes": "While this mitigation is effective for protecting cookies from a browser's own scripting engine, third-party components or plugins may have their own engines that allow access to cookies. Attackers might also be able to use XMLHTTPResponse to read the headers directly and obtain the cookie."
    }
  },
  "References": {
    "Reference": [
      {
        "External_Reference_ID": "REF-2"
      },
      {
        "External_Reference_ID": "REF-3"
      },
      {
        "External_Reference_ID": "REF-4"
      },
      {
        "External_Reference_ID": "REF-5"
      }
    ],
    "Full_Details": [
      {
        "Reference_ID": "REF-2",
        "Author": "OWASP",
        "Title": "HttpOnly",
        "URL": "https://www.owasp.org/index.php/HttpOnly"
      },
      {
        "Reference_ID": "REF-3",
        "Author": "Michael Howard",
        "Title": "Some Bad News and Some Good News",
        "Publication_Year": "2002",
        "URL": "https://msdn.microsoft.com/en-us/library/ms972826.aspx"
      },
      {
        "Reference_ID": "REF-4",
        "Author": "Troy Hunt",
        "Title": "C is for cookie, H is for hacker - understanding HTTP only and Secure cookies",
        "Publication_Year": "2013",
        "URL": "https://www.troyhunt.com/c-is-for-cookie-h-is-for-hacker/"
      },
      {
        "Reference_ID": "REF-5",
        "Author": "Microsoft",
        "Title": "Mitigating Cross-site Scripting With HTTP-only Cookies",
        "URL": "https://msdn.microsoft.com/en-us/library/ms533046.aspx"
      }
    ]
  }
}
```